Update debian changelog and don't enforce apparmor profile in postinst #117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will prevent the install operation from failing on PVH kernels or HVM kernels < 4.14.158
rmol
approved these changes
Dec 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Towards freedomofpress/securedrop-workstation#364
In #116 we've introduced apparmor support but discovered, after merging 2 issues:
To immediately resolve (and not break nightlies), let's merge this ASAP and enforce the apparmor profile via /rw/config/rc.local in the securedrop-workstation salt logic as part of freedomofpress/securedrop-workstation#364
Test plan:
PKG_VERSION=0.0.11 PKG_PATH=../securedrop-client/dist/securedrop-client-0.0.11.tar.gz make securedrop-clientsecuredrop-client_0.0.11+buster_all.deb